Skip to content

Add SHA256 fallback if MD5 isn't available on the system#9535

Merged
nateprewitt merged 3 commits into
v2from
md5_fallback_v2
Jun 9, 2025
Merged

Add SHA256 fallback if MD5 isn't available on the system#9535
nateprewitt merged 3 commits into
v2from
md5_fallback_v2

Conversation

@nateprewitt

Copy link
Copy Markdown
Contributor

Description of changes:
This PR will move our usage of md5 to enable the usedforsecurity flag set to false since these checksumming functions are only intended to create a deterministic path. If MD5 is still not available on the system, we'll attempt to use a FIPS compliant algorithm (SHA256 in this case) to derive an alternative path.

Path names should stay deterministic on similarly configured systems but customers uploading from both FIPS compliant and non-compliant environments to the same bucket may see some redundant uploads for the same template. Risk of this should be low given compliance requirements.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@nateprewitt nateprewitt added the v2 label Jun 6, 2025
@nateprewitt
nateprewitt merged commit 6c0ff5c into v2 Jun 9, 2025
90 checks passed
@nateprewitt
nateprewitt deleted the md5_fallback_v2 branch June 9, 2025 16:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants